Move CI off retired windows-2019 runner image - #11
Merged
Conversation
GitHub retired the windows-2019 hosted runner image on 2025-06-30. Jobs requesting that label are never assigned a runner; they sit queued until the 24 hour limit cancels them, which is why recent "Build and Test" runs show as cancelled at 24h00m rather than failing on a step. Switch both workflows to windows-2022 so jobs are schedulable again. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: e3976c94-4fbf-4be7-a74d-d08a3c592269
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Move CI off the retired
windows-2019runner image.Problem
Both workflows request
runs-on: windows-2019. GitHub retired that hosted runner image on 2025-06-30. A job requesting a label that no longer exists in the hosted pool is not rejected with an error, it simply staysqueueduntil GitHub cancels it at the 24 hour limit.That is why recent
Build and Testruns show as cancelled at 24h00m04s rather than failing on a step, and why PR #10 appears to fail with "a runner was never assigned".This is a pre-existing repository issue, not caused by any open PR. A run on
work/testwas also sitting queued for 4+ hours with the same cause, on a branch unrelated to any pinning work.Change
CI.ymlandpypi_publish.ymlnow usewindows-2022. Theubuntu-latestpublish job is unchanged.Note for reviewers
This also moves the MSVC toolchain off Server 2019, so the
cp39-cp313AMD64 wheel builds compile against a newer toolset. CI on this PR is the first real verification that the wheels still build and the tests still pass.